Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e13b8bba13bc01d147331e4ed9b283a4c70f9932ee1f333e188540c4dfb331

Tx prefix hash: 47352a880705c3523e1eb5cd5279f1babe3691dc4ccd9d636ae8703dc605a862
Tx public key: 75e9d54e4c5295cdcdbaaf1a27236d83ac5b2818b444ed241c1e89950d491355
Timestamp: 1722460069 Timestamp [UCT]: 2024-07-31 21:07:49 Age [y:d:h:m:s]: 00:318:07:39:16
Block: 1077948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227352 RingCT/type: yes/0
Extra: 0175e9d54e4c5295cdcdbaaf1a27236d83ac5b2818b444ed241c1e89950d491355021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e87a1db23b87767a77fabd0c470d59f374fb4c2b3ed59830a221cdc79e35e88 0.600000000000 1550503 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": 1077958, "vin": [ { "gen": { "height": 1077948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e87a1db23b87767a77fabd0c470d59f374fb4c2b3ed59830a221cdc79e35e88" } } ], "extra": [ 1, 117, 233, 213, 78, 76, 82, 149, 205, 205, 186, 175, 26, 39, 35, 109, 131, 172, 91, 40, 24, 180, 68, 237, 36, 28, 30, 137, 149, 13, 73, 19, 85, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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