Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b84bd0f22fc3413a9f8ba9a91238c77297969a06649b5c006aeb2c58b74a8b

Tx prefix hash: 093f06a16839c2654f2a3b3debd60d29ac28611059cd8bad98b4b27387963684
Tx public key: b0c8af24505d7020a0fb465b8ef164162c004e9400de55639d94d6f9cd7c3a40
Timestamp: 1729305395 Timestamp [UCT]: 2024-10-19 02:36:35 Age [y:d:h:m:s]: 01:029:07:51:57
Block: 1134691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279340 RingCT/type: yes/0
Extra: 01b0c8af24505d7020a0fb465b8ef164162c004e9400de55639d94d6f9cd7c3a400211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e64b0e8ba5faba6494c2357297fc0b5a1f338048c277f27a39c7478e918d5c99 0.600000000000 1618016 of 15

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": 1134701, "vin": [ { "gen": { "height": 1134691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e64b0e8ba5faba6494c2357297fc0b5a1f338048c277f27a39c7478e918d5c99" } } ], "extra": [ 1, 176, 200, 175, 36, 80, 93, 112, 32, 160, 251, 70, 91, 142, 241, 100, 22, 44, 0, 78, 148, 0, 222, 85, 99, 157, 148, 214, 249, 205, 124, 58, 64, 2, 17, 0, 0, 0, 2, 31, 10, 83, 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