Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26e95b27a93f5ad1f51277bea22847930b7d4c73f96255b173081fb813887eaf

Tx prefix hash: cb89b35a47c519b8a8b9a976fd23a904f26f6a355bbec5e96850a7ae0dc2926d
Tx public key: 9a520fe446f1a230f4ee08f42fed3432289eaec7d6e8424986bcb028a81cb017
Timestamp: 1711220807 Timestamp [UCT]: 2024-03-23 19:06:47 Age [y:d:h:m:s]: 01:227:06:43:16
Block: 984790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421091 RingCT/type: yes/0
Extra: 019a520fe446f1a230f4ee08f42fed3432289eaec7d6e8424986bcb028a81cb01702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f7889a71d0ca31a39151f7273a3cca01334e1106dc7955c0c82e254050d4bfd 0.600000000000 1444963 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": 984800, "vin": [ { "gen": { "height": 984790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f7889a71d0ca31a39151f7273a3cca01334e1106dc7955c0c82e254050d4bfd" } } ], "extra": [ 1, 154, 82, 15, 228, 70, 241, 162, 48, 244, 238, 8, 244, 47, 237, 52, 50, 40, 158, 174, 199, 214, 232, 66, 73, 134, 188, 176, 40, 168, 28, 176, 23, 2, 17, 0, 0, 0, 4, 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