Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c2134643fd0b3dc004dc706293d118c46f1eb8ebb522249e6c160b81b3e7786

Tx prefix hash: bb9049344e8af862bfdbe8981866dc03a0dd2e774d524fad3527e6afc37c4a85
Tx public key: 7000fe340a8fc6969ec236a4dddbb57e241c4253141d1f0422f0ba4b8d966079
Timestamp: 1728472859 Timestamp [UCT]: 2024-10-09 11:20:59 Age [y:d:h:m:s]: 00:179:21:48:10
Block: 1127794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128368 RingCT/type: yes/0
Extra: 017000fe340a8fc6969ec236a4dddbb57e241c4253141d1f0422f0ba4b8d96607902110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b7bef8f50d63ed7c79cfdaa282d501de09c5ffd12397e8330a4c0e95b352420 0.600000000000 1610607 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": 1127804, "vin": [ { "gen": { "height": 1127794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b7bef8f50d63ed7c79cfdaa282d501de09c5ffd12397e8330a4c0e95b352420" } } ], "extra": [ 1, 112, 0, 254, 52, 10, 143, 198, 150, 158, 194, 54, 164, 221, 219, 181, 126, 36, 28, 66, 83, 20, 29, 31, 4, 34, 240, 186, 75, 141, 150, 96, 121, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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