Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 533ee36efeaacddccf4b7e18ef4ba98f087ba8fcb5b79c81746924343b002f08

Tx prefix hash: 1efbaf4f11110459333ce6dd325ad072fd6126a6fef741225ad4f90af874c3a9
Tx public key: ad534e5af9a3b7b714471756776e7922f29da9647509e46ecbcf54a0abf16fe5
Timestamp: 1673220516 Timestamp [UCT]: 2023-01-08 23:28:36 Age [y:d:h:m:s]: 02:008:20:31:01
Block: 670580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528243 RingCT/type: yes/0
Extra: 01ad534e5af9a3b7b714471756776e7922f29da9647509e46ecbcf54a0abf16fe502110000000252542ceb000000000000000000

1 output(s) for total of 3.682053084000 dcy

stealth address amount amount idx
00: cb1c7ab8beae4d99933085423f3292c48a14d262abded02f0eb3b8e481cf89e6 3.682053084000 1111991 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": 670590, "vin": [ { "gen": { "height": 670580 } } ], "vout": [ { "amount": 3682053084, "target": { "key": "cb1c7ab8beae4d99933085423f3292c48a14d262abded02f0eb3b8e481cf89e6" } } ], "extra": [ 1, 173, 83, 78, 90, 249, 163, 183, 183, 20, 71, 23, 86, 119, 110, 121, 34, 242, 157, 169, 100, 117, 9, 228, 110, 203, 207, 84, 160, 171, 241, 111, 229, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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