Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 190e5956dbd0fd7c8fb6f080e1437ad428b5cf4fbe6b86260c8e043480429c37

Tx prefix hash: 6f2107a2841cfa71fe5583d20685336222e2b1ba029d52fb3000956f83e72773
Tx public key: 2f1ac3b10b92d40a28e9ee63ad8c80440a1cb43a09162400ec5ad4409ee8d16a
Timestamp: 1736073743 Timestamp [UCT]: 2025-01-05 10:42:23 Age [y:d:h:m:s]: 00:102:19:18:21
Block: 1190691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73259 RingCT/type: yes/0
Extra: 012f1ac3b10b92d40a28e9ee63ad8c80440a1cb43a09162400ec5ad4409ee8d16a021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25449d7c807efe532f62214fb8245322c1b4d5c0e4853238fdefcb37bb82489b 0.600000000000 1677208 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": 1190701, "vin": [ { "gen": { "height": 1190691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25449d7c807efe532f62214fb8245322c1b4d5c0e4853238fdefcb37bb82489b" } } ], "extra": [ 1, 47, 26, 195, 177, 11, 146, 212, 10, 40, 233, 238, 99, 173, 140, 128, 68, 10, 28, 180, 58, 9, 22, 36, 0, 236, 90, 212, 64, 158, 232, 209, 106, 2, 17, 0, 0, 0, 3, 223, 195, 186, 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