Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54aa47f5012ba5fe142188ba5d4996b78d07bb962fef8981f93fa1588c98fc52

Tx prefix hash: 7b512580ac8905f4ea8cc135e09353df69f6515c09abe0aa0b2b1806ca4a1106
Tx public key: 15ed85b2fea7f74a31036875c2f0d7e855b8ff4f63f5f1f8b7ff8de70c487945
Timestamp: 1681142465 Timestamp [UCT]: 2023-04-10 16:01:05 Age [y:d:h:m:s]: 02:045:21:30:55
Block: 735652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554999 RingCT/type: yes/0
Extra: 0115ed85b2fea7f74a31036875c2f0d7e855b8ff4f63f5f1f8b7ff8de70c4879450211000000015029cbac000000000000000000

1 output(s) for total of 2.241195617000 dcy

stealth address amount amount idx
00: 276e22caf0ca47bb90cadf8814c3cdd05b419564cef86451800054c7c7d6bdd9 2.241195617000 1181999 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": 735662, "vin": [ { "gen": { "height": 735652 } } ], "vout": [ { "amount": 2241195617, "target": { "key": "276e22caf0ca47bb90cadf8814c3cdd05b419564cef86451800054c7c7d6bdd9" } } ], "extra": [ 1, 21, 237, 133, 178, 254, 167, 247, 74, 49, 3, 104, 117, 194, 240, 215, 232, 85, 184, 255, 79, 99, 245, 241, 248, 183, 255, 141, 231, 12, 72, 121, 69, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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