Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17dd98482d32f0456ee1597d7afd73b60ec04756b7928e0dcea8b868708cda34

Tx prefix hash: a220e0eab1d436d54eb136aa8d60b840ea0cb9d5ceef6e1625a86fcabc428597
Tx public key: b02b0d1690fbbc6a544760a0eeddadb528ccc77fd4c944ca2865054d1dacb4e6
Timestamp: 1721237497 Timestamp [UCT]: 2024-07-17 17:31:37 Age [y:d:h:m:s]: 00:273:04:53:31
Block: 1067826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195174 RingCT/type: yes/0
Extra: 01b02b0d1690fbbc6a544760a0eeddadb528ccc77fd4c944ca2865054d1dacb4e602110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca4b351c0b9c857ddca5fe5219d4a05000fb9c01f8ed9f1ebe235324e1dae5aa 0.600000000000 1538749 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": 1067836, "vin": [ { "gen": { "height": 1067826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca4b351c0b9c857ddca5fe5219d4a05000fb9c01f8ed9f1ebe235324e1dae5aa" } } ], "extra": [ 1, 176, 43, 13, 22, 144, 251, 188, 106, 84, 71, 96, 160, 238, 221, 173, 181, 40, 204, 199, 127, 212, 201, 68, 202, 40, 101, 5, 77, 29, 172, 180, 230, 2, 17, 0, 0, 0, 12, 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