Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 376e4f2b1466a44de2b7f030fca51c6a92c6f72915c9b20c3086f3afcdf28133

Tx prefix hash: 2f34f3f21945b56631eef947568a018137d29b8c845b082393ea7e5b0cf5087d
Tx public key: 1469dd66cb584c41241e08acb507cb7273d62771b6bfa5be28bad592b7899ae7
Timestamp: 1749726614 Timestamp [UCT]: 2025-06-12 11:10:14 Age [y:d:h:m:s]: 00:154:17:35:44
Block: 1303406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108306 RingCT/type: yes/0
Extra: 011469dd66cb584c41241e08acb507cb7273d62771b6bfa5be28bad592b7899ae702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a502e61161b962b48cf4bcfb11dfed01382d06c9e673c6a786ca4ace6388e7a 0.600000000000 1790987 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": 1303416, "vin": [ { "gen": { "height": 1303406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a502e61161b962b48cf4bcfb11dfed01382d06c9e673c6a786ca4ace6388e7a" } } ], "extra": [ 1, 20, 105, 221, 102, 203, 88, 76, 65, 36, 30, 8, 172, 181, 7, 203, 114, 115, 214, 39, 113, 182, 191, 165, 190, 40, 186, 213, 146, 183, 137, 154, 231, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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