Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c25b8c21ce9b3676efde7c48b35d2cbe0b0f0c70358bc37a815f03598471a5ed

Tx prefix hash: f7b0584e9e60ddf744f0a70aad737d9ccb8595652cb6b97c73232ecff1681293
Tx public key: 6f2d140c4db4b73e96fb9423131551442c0a285527511974cc3b5eab08e4c698
Timestamp: 1671889248 Timestamp [UCT]: 2022-12-24 13:40:48 Age [y:d:h:m:s]: 02:118:18:22:34
Block: 659579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 606564 RingCT/type: yes/0
Extra: 016f2d140c4db4b73e96fb9423131551442c0a285527511974cc3b5eab08e4c69802110000000133af99f4000000000000000000

1 output(s) for total of 4.004432166000 dcy

stealth address amount amount idx
00: 28ec391f43d1c563a4fb17ec72e35c58024a5e66fa9a3c2a9da943db9ea0f283 4.004432166000 1100286 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": 659589, "vin": [ { "gen": { "height": 659579 } } ], "vout": [ { "amount": 4004432166, "target": { "key": "28ec391f43d1c563a4fb17ec72e35c58024a5e66fa9a3c2a9da943db9ea0f283" } } ], "extra": [ 1, 111, 45, 20, 12, 77, 180, 183, 62, 150, 251, 148, 35, 19, 21, 81, 68, 44, 10, 40, 85, 39, 81, 25, 116, 204, 59, 94, 171, 8, 228, 198, 152, 2, 17, 0, 0, 0, 1, 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