Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ce442f7ea6f4f23cf314242815a066522fc155b68aaf83b0d2df89f53e73fa1

Tx prefix hash: e784a418ed65681162cc5d1e8b5a933ac738e4df6ed0cde045be7f649f9888ca
Tx public key: 67216c44dce8baf43e87c9739c8a135a84c5939da42a92d9884e4f6ee05d6d9d
Timestamp: 1736246491 Timestamp [UCT]: 2025-01-07 10:41:31 Age [y:d:h:m:s]: 00:090:17:26:04
Block: 1192108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64617 RingCT/type: yes/0
Extra: 0167216c44dce8baf43e87c9739c8a135a84c5939da42a92d9884e4f6ee05d6d9d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 577059f886d7cec6009f1a138ed046ef83798483c996ad808a4d2d0fc9ac4143 0.600000000000 1678655 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": 1192118, "vin": [ { "gen": { "height": 1192108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "577059f886d7cec6009f1a138ed046ef83798483c996ad808a4d2d0fc9ac4143" } } ], "extra": [ 1, 103, 33, 108, 68, 220, 232, 186, 244, 62, 135, 201, 115, 156, 138, 19, 90, 132, 197, 147, 157, 164, 42, 146, 217, 136, 78, 79, 110, 224, 93, 109, 157, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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