Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 321a53f0dfaed6a837a5b9a3dfea616e89973aa24ee29fb30a0b85c2a5e1c51f

Tx prefix hash: e94374822b47a4486d1ae499931d962e5cc9e6b8b3c5894097158d0345a502e4
Tx public key: 28feb8656566382b4f3e77d2b08013a8fe8e21e322300f908ab797fd3f3c6fa0
Timestamp: 1705100135 Timestamp [UCT]: 2024-01-12 22:55:35 Age [y:d:h:m:s]: 01:104:10:17:58
Block: 934016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335756 RingCT/type: yes/0
Extra: 0128feb8656566382b4f3e77d2b08013a8fe8e21e322300f908ab797fd3f3c6fa002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc55729169b0a7e53cfb30eccc980c21f2114e29257f278ab4ee044a8b4e6625 0.600000000000 1392002 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 934026, "vin": [ { "gen": { "height": 934016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc55729169b0a7e53cfb30eccc980c21f2114e29257f278ab4ee044a8b4e6625" } } ], "extra": [ 1, 40, 254, 184, 101, 101, 102, 56, 43, 79, 62, 119, 210, 176, 128, 19, 168, 254, 142, 33, 227, 34, 48, 15, 144, 138, 183, 151, 253, 63, 60, 111, 160, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8