Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44c11f5612a595f4601faefb8523754c73e24f64d94c42994315a4f58f6917b

Tx prefix hash: fd59d915adfdb29a2c18c4975e8f55b88a45e61fb0bed43c2642eb2c5616d5d8
Tx public key: d17eb9b2e757e2768349a7dbbf9f2bd4422df6f48a638e7e364c4264e1c6c921
Timestamp: 1710381519 Timestamp [UCT]: 2024-03-14 01:58:39 Age [y:d:h:m:s]: 01:064:05:11:08
Block: 977832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306897 RingCT/type: yes/0
Extra: 01d17eb9b2e757e2768349a7dbbf9f2bd4422df6f48a638e7e364c4264e1c6c9210211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7d92fd313e3b1fa8d5ddaebabfba2675fa60983bee30331d0587d9d1a194d56 0.600000000000 1437839 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": 977842, "vin": [ { "gen": { "height": 977832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7d92fd313e3b1fa8d5ddaebabfba2675fa60983bee30331d0587d9d1a194d56" } } ], "extra": [ 1, 209, 126, 185, 178, 231, 87, 226, 118, 131, 73, 167, 219, 191, 159, 43, 212, 66, 45, 246, 244, 138, 99, 142, 126, 54, 76, 66, 100, 225, 198, 201, 33, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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