Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4080c67039a235100aa654a93cdd9b7b3356faf11251a4d240798311b1cd9f

Tx prefix hash: 0d6735e5f125853e80a404b59f0db2e783a4d74cd4f67ba9a4e5b3f78f167834
Tx public key: aafc45aa373fdf8560b5e23b61057e635fa18c591c0ed0a4b76d29355ca8f8b0
Timestamp: 1666335079 Timestamp [UCT]: 2022-10-21 06:51:19 Age [y:d:h:m:s]: 03:010:16:29:23
Block: 613659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 787884 RingCT/type: yes/0
Extra: 01aafc45aa373fdf8560b5e23b61057e635fa18c591c0ed0a4b76d29355ca8f8b002110000000e33af99f4000000000000000000

1 output(s) for total of 5.684509948000 dcy

stealth address amount amount idx
00: e5cd1da67488d4b9f21fa7134136d8fd5d825f4153eec37bed98416a4054df29 5.684509948000 1050974 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": 613669, "vin": [ { "gen": { "height": 613659 } } ], "vout": [ { "amount": 5684509948, "target": { "key": "e5cd1da67488d4b9f21fa7134136d8fd5d825f4153eec37bed98416a4054df29" } } ], "extra": [ 1, 170, 252, 69, 170, 55, 63, 223, 133, 96, 181, 226, 59, 97, 5, 126, 99, 95, 161, 140, 89, 28, 14, 208, 164, 183, 109, 41, 53, 92, 168, 248, 176, 2, 17, 0, 0, 0, 14, 51, 175, 153, 244, 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