Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ecbe40e8024ea06f13bc320fa0e08ac98fd43e8ab6fe094dc204414f4d57ef5

Tx prefix hash: 79a48333c06e71aae386c08eb74b48f40db4c366ce4aa98bde7c73b423edb2db
Tx public key: 10d2a7eef7790b63c7bdf0a63149c270b2fa84871a017b9430b9dc152201cf4c
Timestamp: 1718920514 Timestamp [UCT]: 2024-06-20 21:55:14 Age [y:d:h:m:s]: 00:357:12:25:17
Block: 1048598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255484 RingCT/type: yes/0
Extra: 0110d2a7eef7790b63c7bdf0a63149c270b2fa84871a017b9430b9dc152201cf4c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf08d636ce55aa41276dca89ecfd54c23672c78204c06cbcf57e02654d2476d0 0.600000000000 1518683 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": 1048608, "vin": [ { "gen": { "height": 1048598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf08d636ce55aa41276dca89ecfd54c23672c78204c06cbcf57e02654d2476d0" } } ], "extra": [ 1, 16, 210, 167, 238, 247, 121, 11, 99, 199, 189, 240, 166, 49, 73, 194, 112, 178, 250, 132, 135, 26, 1, 123, 148, 48, 185, 220, 21, 34, 1, 207, 76, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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