Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac6f7730644e89289d777f2a38126bf88721ada692fce16c9a855b34ca4760b3

Tx prefix hash: a5f78da5707cbdf32e5491284981b5f197661bfb744dd26c9b67a8e917786947
Tx public key: 091c2b0d084a54a0e64d0ecc3f462c1cfc2b6b5d7d1bf87636c8c98e918c8f4d
Timestamp: 1709367477 Timestamp [UCT]: 2024-03-02 08:17:57 Age [y:d:h:m:s]: 00:243:16:22:21
Block: 969416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174467 RingCT/type: yes/0
Extra: 01091c2b0d084a54a0e64d0ecc3f462c1cfc2b6b5d7d1bf87636c8c98e918c8f4d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a33524a0aba2e48a1a7ba1df3af8c411cde1f82a08a462d4fbc5decd9f27e84 0.600000000000 1429245 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": 969426, "vin": [ { "gen": { "height": 969416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a33524a0aba2e48a1a7ba1df3af8c411cde1f82a08a462d4fbc5decd9f27e84" } } ], "extra": [ 1, 9, 28, 43, 13, 8, 74, 84, 160, 230, 77, 14, 204, 63, 70, 44, 28, 252, 43, 107, 93, 125, 27, 248, 118, 54, 200, 201, 142, 145, 140, 143, 77, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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