Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a14505cf7998220129310ff8193867cd078a0a5f8f1976fbdfe7a239bb17da8d

Tx prefix hash: a2469a781893982e3452fb3fd6a0bf44f4b249c2edc5b41e1deba5527008f98a
Tx public key: 73ad0337926d387395902a1bc5ca4efb455f64b5c8b3c6aa203cc0a5c1becfb4
Timestamp: 1711402459 Timestamp [UCT]: 2024-03-25 21:34:19 Age [y:d:h:m:s]: 01:052:02:42:10
Block: 986299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298222 RingCT/type: yes/0
Extra: 0173ad0337926d387395902a1bc5ca4efb455f64b5c8b3c6aa203cc0a5c1becfb402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46907f410411ed3b514e504b7d2c7a471bb016a4eb0500f312e248ceade8431c 0.600000000000 1446528 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": 986309, "vin": [ { "gen": { "height": 986299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46907f410411ed3b514e504b7d2c7a471bb016a4eb0500f312e248ceade8431c" } } ], "extra": [ 1, 115, 173, 3, 55, 146, 109, 56, 115, 149, 144, 42, 27, 197, 202, 78, 251, 69, 95, 100, 181, 200, 179, 198, 170, 32, 60, 192, 165, 193, 190, 207, 180, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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