Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e9ef88a51706bcc03f630739a15ab754b0acd1511547bbd6a27089ed45d40df

Tx prefix hash: 9cf897f9f59ae14cb60598c3378f26b8abb49a4739cc0e9d0d297c97f0cf607a
Tx public key: d1be759b3acf58bb093f37e1cb4947f3a4bc5a44a011dd79271e90ac1a54511c
Timestamp: 1710456185 Timestamp [UCT]: 2024-03-14 22:43:05 Age [y:d:h:m:s]: 01:044:15:09:43
Block: 978455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292885 RingCT/type: yes/0
Extra: 01d1be759b3acf58bb093f37e1cb4947f3a4bc5a44a011dd79271e90ac1a54511c02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9589e6df38f98ac50b50e75a0ae69255179c95d8a960395d9306a0634107ce 0.600000000000 1438482 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": 978465, "vin": [ { "gen": { "height": 978455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9589e6df38f98ac50b50e75a0ae69255179c95d8a960395d9306a0634107ce" } } ], "extra": [ 1, 209, 190, 117, 155, 58, 207, 88, 187, 9, 63, 55, 225, 203, 73, 71, 243, 164, 188, 90, 68, 160, 17, 221, 121, 39, 30, 144, 172, 26, 84, 81, 28, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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