Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fac52e78b682d8f8b886f0457614a4199b14dd2774c2bcabec30b1acd395e331

Tx prefix hash: 2084eb9854577b61d413c741305027f3a6036b2114bc9097216f6bb938d6dfa3
Tx public key: e56e12494c5e1739ee589cd10e096dbc4d93bc6f7bc5d0fc456f8fa0421f68d4
Timestamp: 1743328739 Timestamp [UCT]: 2025-03-30 09:58:59 Age [y:d:h:m:s]: 00:304:01:30:13
Block: 1250471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214963 RingCT/type: yes/0
Extra: 01e56e12494c5e1739ee589cd10e096dbc4d93bc6f7bc5d0fc456f8fa0421f68d40211000000061a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 133d9734ff4882a6a265a8fe4d32f8ec346e77db7a0aa5f3a6f6cbe30b82add5 0.600000000000 1737520 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": 1250481, "vin": [ { "gen": { "height": 1250471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "133d9734ff4882a6a265a8fe4d32f8ec346e77db7a0aa5f3a6f6cbe30b82add5" } } ], "extra": [ 1, 229, 110, 18, 73, 76, 94, 23, 57, 238, 88, 156, 209, 14, 9, 109, 188, 77, 147, 188, 111, 123, 197, 208, 252, 69, 111, 143, 160, 66, 31, 104, 212, 2, 17, 0, 0, 0, 6, 26, 151, 4, 3, 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