Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30bf91a75cbe9586c9a97bc9499dcf44ddd11fcd78e37dc6597a830eda0db648

Tx prefix hash: a520bff78e4c1ca80a6bea955ce86c3a0826079e07be2d6674f99e66f4c2c79b
Tx public key: fb868cb8e8a0d21df8dcff66db6ce5c9d1c6ad9e2be150a7242989ed5b45a1dc
Timestamp: 1700221099 Timestamp [UCT]: 2023-11-17 11:38:19 Age [y:d:h:m:s]: 01:144:06:02:49
Block: 893588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364264 RingCT/type: yes/0
Extra: 01fb868cb8e8a0d21df8dcff66db6ce5c9d1c6ad9e2be150a7242989ed5b45a1dc02110000001d33af99f4000000000000000000

1 output(s) for total of 0.671694826000 dcy

stealth address amount amount idx
00: cdaa6ffff69f8a684bf868628f2fe6f4b283b2a86d146d88d9ba3de861024e94 0.671694826000 1349771 of 0

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": 893598, "vin": [ { "gen": { "height": 893588 } } ], "vout": [ { "amount": 671694826, "target": { "key": "cdaa6ffff69f8a684bf868628f2fe6f4b283b2a86d146d88d9ba3de861024e94" } } ], "extra": [ 1, 251, 134, 140, 184, 232, 160, 210, 29, 248, 220, 255, 102, 219, 108, 229, 201, 209, 198, 173, 158, 43, 225, 80, 167, 36, 41, 137, 237, 91, 69, 161, 220, 2, 17, 0, 0, 0, 29, 51, 175, 153, 244, 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