Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 411f3f4cad7eae8fcea8803bc230578b5ee997c63a33678a7c6cfd0b52e0807f

Tx prefix hash: c3c8d56fff80a3c65b6452b8c39036b640a7b65b52ef11001bad119da8716473
Tx public key: 412b096c55a48000838724a3e340b2702e5e692963981ae006a6fd305f335e0b
Timestamp: 1722908675 Timestamp [UCT]: 2024-08-06 01:44:35 Age [y:d:h:m:s]: 00:139:21:44:31
Block: 1081669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100112 RingCT/type: yes/0
Extra: 01412b096c55a48000838724a3e340b2702e5e692963981ae006a6fd305f335e0b021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b545427f5e41d5e6d60efe7485d64c399f44743a5f03eec5fd6a2fa7ca60966 0.600000000000 1555486 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": 1081679, "vin": [ { "gen": { "height": 1081669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b545427f5e41d5e6d60efe7485d64c399f44743a5f03eec5fd6a2fa7ca60966" } } ], "extra": [ 1, 65, 43, 9, 108, 85, 164, 128, 0, 131, 135, 36, 163, 227, 64, 178, 112, 46, 94, 105, 41, 99, 152, 26, 224, 6, 166, 253, 48, 95, 51, 94, 11, 2, 17, 0, 0, 0, 9, 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