Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 382eb180136f00ca054cd36226edf068c579df26c132fd7914e7789049f89b70

Tx prefix hash: c67d0bfc42af89f4f45362058dfd2a55239336b050676688342cf55000ce64dd
Tx public key: 6759fbb9bda1a7a9b04ef5e050c7588f9a2d46402ee6de7bf89928209a4e4d1b
Timestamp: 1695621795 Timestamp [UCT]: 2023-09-25 06:03:15 Age [y:d:h:m:s]: 01:186:03:34:53
Block: 855647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394100 RingCT/type: yes/0
Extra: 016759fbb9bda1a7a9b04ef5e050c7588f9a2d46402ee6de7bf89928209a4e4d1b02110000000433af99f4000000000000000000

1 output(s) for total of 0.897193960000 dcy

stealth address amount amount idx
00: ae5f786fc46cf7ea2e2a86622c136140387284e0e76d02fde41beae3f08f2aca 0.897193960000 1309679 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": 855657, "vin": [ { "gen": { "height": 855647 } } ], "vout": [ { "amount": 897193960, "target": { "key": "ae5f786fc46cf7ea2e2a86622c136140387284e0e76d02fde41beae3f08f2aca" } } ], "extra": [ 1, 103, 89, 251, 185, 189, 161, 167, 169, 176, 78, 245, 224, 80, 199, 88, 143, 154, 45, 70, 64, 46, 230, 222, 123, 248, 153, 40, 32, 154, 78, 77, 27, 2, 17, 0, 0, 0, 4, 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