Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 815c9c3b3103d6b7dbfa06bbdccaddbc654ba7a7ff10f849a14ed3342957ea8b

Tx prefix hash: 97522b9c11c8ffc401032ecf67b4d449d7fbdb4fecf0948249dd056b47ff70cb
Tx public key: 785640b93cc94709a048852f7daaf0fcfdc5ac51d68b33256a91c1832f39be12
Timestamp: 1696172700 Timestamp [UCT]: 2023-10-01 15:05:00 Age [y:d:h:m:s]: 01:217:12:19:42
Block: 860214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416529 RingCT/type: yes/0
Extra: 01785640b93cc94709a048852f7daaf0fcfdc5ac51d68b33256a91c1832f39be1202110000000633af99f4000000000000000000

1 output(s) for total of 0.866470872000 dcy

stealth address amount amount idx
00: fbfe6039c001cd9f584d7ccb8a11b1f75c0a83086576d1fd781604df920df865 0.866470872000 1314486 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": 860224, "vin": [ { "gen": { "height": 860214 } } ], "vout": [ { "amount": 866470872, "target": { "key": "fbfe6039c001cd9f584d7ccb8a11b1f75c0a83086576d1fd781604df920df865" } } ], "extra": [ 1, 120, 86, 64, 185, 60, 201, 71, 9, 160, 72, 133, 47, 125, 170, 240, 252, 253, 197, 172, 81, 214, 139, 51, 37, 106, 145, 193, 131, 47, 57, 190, 18, 2, 17, 0, 0, 0, 6, 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