Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d828274019f318b187b731390aa1e86573edea701d7b33e83ce14505e3702810

Tx prefix hash: 1a1b4235265c33b46f49bb93f44618d6129de3f7c76ad4d0864228249c626c26
Tx public key: 371a0ed1a72a2ca916de8bfa7de0d147cc04876d98b0ee9e94d58285b325d371
Timestamp: 1695624529 Timestamp [UCT]: 2023-09-25 06:48:49 Age [y:d:h:m:s]: 01:114:10:31:25
Block: 855672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343071 RingCT/type: yes/0
Extra: 01371a0ed1a72a2ca916de8bfa7de0d147cc04876d98b0ee9e94d58285b325d3710211000000094b8f5122000000000000000000

1 output(s) for total of 0.897022850000 dcy

stealth address amount amount idx
00: 78214df8c1218e5e81e41297d25ff6dc467cc5447e345f54bf273fe2e209fdbf 0.897022850000 1309704 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": 855682, "vin": [ { "gen": { "height": 855672 } } ], "vout": [ { "amount": 897022850, "target": { "key": "78214df8c1218e5e81e41297d25ff6dc467cc5447e345f54bf273fe2e209fdbf" } } ], "extra": [ 1, 55, 26, 14, 209, 167, 42, 44, 169, 22, 222, 139, 250, 125, 224, 209, 71, 204, 4, 135, 109, 152, 176, 238, 158, 148, 213, 130, 133, 179, 37, 211, 113, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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