Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a878269710a4a7eb8fe0d0afc33ac5dc4d2b2b710b2da3c53a79ba01effc161

Tx prefix hash: e269e7a17002b8547abc8f3e28ee6252d04e5aff716abbc0b153fba0bd120f6f
Tx public key: 460ec48e51b3d4e0e816643e93e5831b6d550361bc40445e6d84a69c27875998
Timestamp: 1717486152 Timestamp [UCT]: 2024-06-04 07:29:12 Age [y:d:h:m:s]: 00:300:08:25:32
Block: 1036728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214637 RingCT/type: yes/0
Extra: 01460ec48e51b3d4e0e816643e93e5831b6d550361bc40445e6d84a69c2787599802110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f578d19b83a3e88fad9cb6252d03b309ee90caf650e9934861a7dcff39913e2c 0.600000000000 1505257 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": 1036738, "vin": [ { "gen": { "height": 1036728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f578d19b83a3e88fad9cb6252d03b309ee90caf650e9934861a7dcff39913e2c" } } ], "extra": [ 1, 70, 14, 196, 142, 81, 179, 212, 224, 232, 22, 100, 62, 147, 229, 131, 27, 109, 85, 3, 97, 188, 64, 68, 94, 109, 132, 166, 156, 39, 135, 89, 152, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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