Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26492715028b5e450701b3056b2d7638e7426b3410290192167307e9ae653df5

Tx prefix hash: 4de323e2218d9513da7cbff422a115e4e6a40338f57a1a451f8adc8eec61303d
Tx public key: f7774430145a19a4e92754324bc66549e2d7cbdb75e565315e3bef73507b3131
Timestamp: 1729728516 Timestamp [UCT]: 2024-10-24 00:08:36 Age [y:d:h:m:s]: 00:031:04:40:53
Block: 1138180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22276 RingCT/type: yes/0
Extra: 01f7774430145a19a4e92754324bc66549e2d7cbdb75e565315e3bef73507b31310211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 189d91f61d14fd2d6876178cf59af3d1b3fdde2fda3f3c049a0f5099df97f5f9 0.600000000000 1621797 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": 1138190, "vin": [ { "gen": { "height": 1138180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "189d91f61d14fd2d6876178cf59af3d1b3fdde2fda3f3c049a0f5099df97f5f9" } } ], "extra": [ 1, 247, 119, 68, 48, 20, 90, 25, 164, 233, 39, 84, 50, 75, 198, 101, 73, 226, 215, 203, 219, 117, 229, 101, 49, 94, 59, 239, 115, 80, 123, 49, 49, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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