Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6da9991c34e2c1394a2fedb4976b4db2277835f7bd1d9f9b16362d912468434f

Tx prefix hash: 0ef07277e5526526fa4ebe255b07efb9cb8079653ecaba7d99a5267e6958365a
Tx public key: 8a308b3ae5bc2b1fba250054daa95d13a0e3d85df0064a8d1784ac2cb4e2cac1
Timestamp: 1742730691 Timestamp [UCT]: 2025-03-23 11:51:31 Age [y:d:h:m:s]: 00:255:05:17:38
Block: 1245531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180161 RingCT/type: yes/0
Extra: 018a308b3ae5bc2b1fba250054daa95d13a0e3d85df0064a8d1784ac2cb4e2cac1021100000001af845649000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18e7bb68dbe18ac2f37438b063fbcec9d71dd52efec4fe4134081aed06641b97 0.600000000000 1732522 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": 1245541, "vin": [ { "gen": { "height": 1245531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18e7bb68dbe18ac2f37438b063fbcec9d71dd52efec4fe4134081aed06641b97" } } ], "extra": [ 1, 138, 48, 139, 58, 229, 188, 43, 31, 186, 37, 0, 84, 218, 169, 93, 19, 160, 227, 216, 93, 240, 6, 74, 141, 23, 132, 172, 44, 180, 226, 202, 193, 2, 17, 0, 0, 0, 1, 175, 132, 86, 73, 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