Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc439ac21c00e3f8029d90ef77a43a4ea5df48edeb84be00f7a62bed52f3080

Tx prefix hash: 865d5b6ac8595bad75c216a24eddf9a618056f6628d2b1617d26739c07a93762
Tx public key: 130337582d39a4ea4adc4997ef5ecd569b4e5bed1a895ee793fa1cf7b01e7bdc
Timestamp: 1575977907 Timestamp [UCT]: 2019-12-10 11:38:27 Age [y:d:h:m:s]: 05:031:05:37:01
Block: 24861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168157 RingCT/type: yes/0
Extra: 01130337582d39a4ea4adc4997ef5ecd569b4e5bed1a895ee793fa1cf7b01e7bdc02110000000f9159db1e000000000000000000

1 output(s) for total of 507.722086959000 dcy

stealth address amount amount idx
00: e34cdd7ed313dd4aa6058a149b7dd98152cd5370a84d08071133624d06b23a7c 507.722086959000 40826 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": 24871, "vin": [ { "gen": { "height": 24861 } } ], "vout": [ { "amount": 507722086959, "target": { "key": "e34cdd7ed313dd4aa6058a149b7dd98152cd5370a84d08071133624d06b23a7c" } } ], "extra": [ 1, 19, 3, 55, 88, 45, 57, 164, 234, 74, 220, 73, 151, 239, 94, 205, 86, 155, 78, 91, 237, 26, 137, 94, 231, 147, 250, 28, 247, 176, 30, 123, 220, 2, 17, 0, 0, 0, 15, 145, 89, 219, 30, 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