Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cce2be60536a36cdb9290ff581fb2aceca0b8abdaa3cb6f94c0eec159f1a92a6

Tx prefix hash: d1214392f1c230c9a8238c182a54e42633e24d109f42bce86b4fe903d4178956
Tx public key: dc150d073a51e2ecdbeaf398b344fba84f49614e7eb378ce0c96ae12143e80d3
Timestamp: 1724033793 Timestamp [UCT]: 2024-08-19 02:16:33 Age [y:d:h:m:s]: 00:229:01:42:26
Block: 1091000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163580 RingCT/type: yes/0
Extra: 01dc150d073a51e2ecdbeaf398b344fba84f49614e7eb378ce0c96ae12143e80d3021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 895e0e9347e4b1a71bbfb1e9ee6d4facf7e76486ae25865a7e6e8426142723e5 0.600000000000 1565625 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": 1091010, "vin": [ { "gen": { "height": 1091000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "895e0e9347e4b1a71bbfb1e9ee6d4facf7e76486ae25865a7e6e8426142723e5" } } ], "extra": [ 1, 220, 21, 13, 7, 58, 81, 226, 236, 219, 234, 243, 152, 179, 68, 251, 168, 79, 73, 97, 78, 126, 179, 120, 206, 12, 150, 174, 18, 20, 62, 128, 211, 2, 17, 0, 0, 0, 2, 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