Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 461f572bd3a10cfc0c8c30bcae442c909026cb77724904ae7091c44e6fe2b1ad

Tx prefix hash: c158f24358dd00e8ee0bcccf0f7ceeb9288bb9cc3bd03fcde58ffdd6989825a7
Tx public key: 779ba4f6752bb9ad1589f819e2f781f0aef8deda6e69600ed3bc4dad1bc9cc65
Timestamp: 1710539173 Timestamp [UCT]: 2024-03-15 21:46:13 Age [y:d:h:m:s]: 00:257:16:45:11
Block: 979143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184474 RingCT/type: yes/0
Extra: 01779ba4f6752bb9ad1589f819e2f781f0aef8deda6e69600ed3bc4dad1bc9cc6502110000000f7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6d2b165f850f4dfc2e1c200bfef64aa3e1c850300076f2f1b411258ada827a6 0.600000000000 1439176 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": 979153, "vin": [ { "gen": { "height": 979143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6d2b165f850f4dfc2e1c200bfef64aa3e1c850300076f2f1b411258ada827a6" } } ], "extra": [ 1, 119, 155, 164, 246, 117, 43, 185, 173, 21, 137, 248, 25, 226, 247, 129, 240, 174, 248, 222, 218, 110, 105, 96, 14, 211, 188, 77, 173, 27, 201, 204, 101, 2, 17, 0, 0, 0, 15, 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