Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30106974b68aa2fde74dfa8769013105910b295c9d0360785a6ae1ef4c1b96a7

Tx prefix hash: 16b304fa3524b02e797cef47e8e4fa2da8346e81d70b925f66fcd988fc664bd5
Tx public key: ef3c9bcea96686f38b0728284f77f18a5f54ebb5f84eb618dc71250bd1f4545e
Timestamp: 1717360960 Timestamp [UCT]: 2024-06-02 20:42:40 Age [y:d:h:m:s]: 01:164:14:03:01
Block: 1035676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376217 RingCT/type: yes/0
Extra: 01ef3c9bcea96686f38b0728284f77f18a5f54ebb5f84eb618dc71250bd1f4545e0211000000014385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e50f40b7d13165af49fd6223c09e762b12e46a9da2d03a0f1776f78705a63fa7 0.600000000000 1504199 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": 1035686, "vin": [ { "gen": { "height": 1035676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e50f40b7d13165af49fd6223c09e762b12e46a9da2d03a0f1776f78705a63fa7" } } ], "extra": [ 1, 239, 60, 155, 206, 169, 102, 134, 243, 139, 7, 40, 40, 79, 119, 241, 138, 95, 84, 235, 181, 248, 78, 182, 24, 220, 113, 37, 11, 209, 244, 84, 94, 2, 17, 0, 0, 0, 1, 67, 133, 54, 42, 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