Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90356f3d26848d34f813898f07ef9c1fb7287b9dd21599f536b016576fddd62c

Tx prefix hash: a4b129ece8d05c3490bd497c4ac7a82b85afb72d1539f5a45e7a6f25bc3bda5d
Tx public key: 41ed9ed0fd8ec5a85a3be632af3f9bdcd0abc602fe872d506462d6f758435394
Timestamp: 1713975274 Timestamp [UCT]: 2024-04-24 16:14:34 Age [y:d:h:m:s]: 00:217:18:19:21
Block: 1007607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155887 RingCT/type: yes/0
Extra: 0141ed9ed0fd8ec5a85a3be632af3f9bdcd0abc602fe872d506462d6f75843539402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab7c6159f6eae8237e856242e4baca4d5b143862958ada5fe9b93a2c6ca07159 0.600000000000 1469003 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": 1007617, "vin": [ { "gen": { "height": 1007607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab7c6159f6eae8237e856242e4baca4d5b143862958ada5fe9b93a2c6ca07159" } } ], "extra": [ 1, 65, 237, 158, 208, 253, 142, 197, 168, 90, 59, 230, 50, 175, 63, 155, 220, 208, 171, 198, 2, 254, 135, 45, 80, 100, 98, 214, 247, 88, 67, 83, 148, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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