Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16527b36f91201d718f7cdfec0d0dee9c090876d1e737af1d3398e0fd86b38dd

Tx prefix hash: 1cbd26a87d8e2921f8dfe384eebcba66379fbb05037d6e25d671bfbbee864cb3
Tx public key: 1c779b37c661bcb6b1a4777a9be7d18dd746455bd2c6eff6fb8ed0e84f4eb3aa
Timestamp: 1574521756 Timestamp [UCT]: 2019-11-23 15:09:16 Age [y:d:h:m:s]: 05:343:16:14:55
Block: 15645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1386134 RingCT/type: yes/0
Extra: 011c779b37c661bcb6b1a4777a9be7d18dd746455bd2c6eff6fb8ed0e84f4eb3aa021100000013fc8b7a00000000000000000000

1 output(s) for total of 544.706432156000 dcy

stealth address amount amount idx
00: 4ac2aa12362d216f5a92b4c4967f2c1eeafa8faaa4a0ab61f7b876648e3139d2 544.706432156000 21153 of 0

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": 15655, "vin": [ { "gen": { "height": 15645 } } ], "vout": [ { "amount": 544706432156, "target": { "key": "4ac2aa12362d216f5a92b4c4967f2c1eeafa8faaa4a0ab61f7b876648e3139d2" } } ], "extra": [ 1, 28, 119, 155, 55, 198, 97, 188, 182, 177, 164, 119, 122, 155, 231, 209, 141, 215, 70, 69, 91, 210, 198, 239, 246, 251, 142, 208, 232, 79, 78, 179, 170, 2, 17, 0, 0, 0, 19, 252, 139, 122, 0, 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