Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e399fbcebc46ce2486139042f138ae8c159b9c8e4ee6bc6d80f62507cb1b5a47

Tx prefix hash: 93cee4b74a73f388e3fda928df7aff1ecdd7aa6ce37ca7fe63de69539ac5d9b8
Tx public key: 4ff158ca20abfc0e58b4ec015b717bc172f9ee131f765191d2071146820ae139
Timestamp: 1632448444 Timestamp [UCT]: 2021-09-24 01:54:04 Age [y:d:h:m:s]: 03:131:13:42:28
Block: 339778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870093 RingCT/type: yes/0
Extra: 014ff158ca20abfc0e58b4ec015b717bc172f9ee131f765191d2071146820ae139021100000010f60c5d7e000000000000000000

1 output(s) for total of 45.940354746000 dcy

stealth address amount amount idx
00: 0f87d666ddf115af0df6b4cc68d8738aad2932fcc9e2bb3d36fca2e28ffdf067 45.940354746000 698675 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": 339788, "vin": [ { "gen": { "height": 339778 } } ], "vout": [ { "amount": 45940354746, "target": { "key": "0f87d666ddf115af0df6b4cc68d8738aad2932fcc9e2bb3d36fca2e28ffdf067" } } ], "extra": [ 1, 79, 241, 88, 202, 32, 171, 252, 14, 88, 180, 236, 1, 91, 113, 123, 193, 114, 249, 238, 19, 31, 118, 81, 145, 210, 7, 17, 70, 130, 10, 225, 57, 2, 17, 0, 0, 0, 16, 246, 12, 93, 126, 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