Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d9e27f5099a32fcf46ba412658a39f39ccf7dc7cf05969a73e046ce1ba094c1

Tx prefix hash: 057833ee3e604f26e42dd77853602fd67d051362329644612ee1680ba1b02881
Tx public key: 24d7123f67b0d1ff590db0150cb0f8315247bfc1adddad39a0bad73e820e1cdd
Timestamp: 1712058248 Timestamp [UCT]: 2024-04-02 11:44:08 Age [y:d:h:m:s]: 00:329:00:33:49
Block: 991687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235237 RingCT/type: yes/0
Extra: 0124d7123f67b0d1ff590db0150cb0f8315247bfc1adddad39a0bad73e820e1cdd0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f532d3c7d1a2947c2ef76ca49e2cf3ff2586f887b04fd25d4b40896fba6f3cd2 0.600000000000 1452023 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": 991697, "vin": [ { "gen": { "height": 991687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f532d3c7d1a2947c2ef76ca49e2cf3ff2586f887b04fd25d4b40896fba6f3cd2" } } ], "extra": [ 1, 36, 215, 18, 63, 103, 176, 209, 255, 89, 13, 176, 21, 12, 176, 248, 49, 82, 71, 191, 193, 173, 221, 173, 57, 160, 186, 215, 62, 130, 14, 28, 221, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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