Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c9e080d2e79c946c674c268a819ade87530c5a0c7a2f48eaf9cc0a932d8de8a

Tx prefix hash: bbceb620a7218338cbd980428cda5f0b8a45c6b03edb584962229d4a6b59b255
Tx public key: 2f0c4920e1f910726fb8cbc408183644122b467580083213a80ff36756e65ba3
Timestamp: 1716683159 Timestamp [UCT]: 2024-05-26 00:25:59 Age [y:d:h:m:s]: 00:332:16:53:26
Block: 1030061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237792 RingCT/type: yes/0
Extra: 012f0c4920e1f910726fb8cbc408183644122b467580083213a80ff36756e65ba30211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f221d426b12dbbb7e4edbc70a4a7b6d57c6748e3b884de2e298308907e580fa2 0.600000000000 1498314 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": 1030071, "vin": [ { "gen": { "height": 1030061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f221d426b12dbbb7e4edbc70a4a7b6d57c6748e3b884de2e298308907e580fa2" } } ], "extra": [ 1, 47, 12, 73, 32, 225, 249, 16, 114, 111, 184, 203, 196, 8, 24, 54, 68, 18, 43, 70, 117, 128, 8, 50, 19, 168, 15, 243, 103, 86, 230, 91, 163, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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