Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3676d405d85282a0233a78e667f7d0f640e2c72f9a5a3e09e386ac95d9bf898c

Tx prefix hash: 034906a5042e6da6d96ea856fa6423955e737c0e01893a3e884b5dcb3e5b8950
Tx public key: 29f7f055977922dead445d42fe691d3b2fca590ffc7dbf8f3bb186366036eab5
Timestamp: 1730707497 Timestamp [UCT]: 2024-11-04 08:04:57 Age [y:d:h:m:s]: 00:020:07:58:26
Block: 1146231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14565 RingCT/type: yes/0
Extra: 0129f7f055977922dead445d42fe691d3b2fca590ffc7dbf8f3bb186366036eab50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18fa198ce34a1d0e2285d2fae1a12ccc56e858c6b669a63cfa84101a82557d92 0.600000000000 1630830 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": 1146241, "vin": [ { "gen": { "height": 1146231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18fa198ce34a1d0e2285d2fae1a12ccc56e858c6b669a63cfa84101a82557d92" } } ], "extra": [ 1, 41, 247, 240, 85, 151, 121, 34, 222, 173, 68, 93, 66, 254, 105, 29, 59, 47, 202, 89, 15, 252, 125, 191, 143, 59, 177, 134, 54, 96, 54, 234, 181, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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