Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb8ebf29b0bd4215e7fd1d086e6e1bea8165c93876ccb7599d97cda4d890ab4d

Tx prefix hash: c592bd5dab0eeb813a268f48653480b839004aa3ae1504d65b6810be531d9f2b
Tx public key: 4184990436ffd70f053f84dc2c17f8d357e090312f248a5f55ed8c7205391b7a
Timestamp: 1707006796 Timestamp [UCT]: 2024-02-04 00:33:16 Age [y:d:h:m:s]: 01:025:15:36:29
Block: 949814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279377 RingCT/type: yes/0
Extra: 014184990436ffd70f053f84dc2c17f8d357e090312f248a5f55ed8c7205391b7a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7be4035bb9c9d9fe11955795f850e25ab95a23bd85b341b1b51d5ad9018e60b 0.600000000000 1408346 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": 949824, "vin": [ { "gen": { "height": 949814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7be4035bb9c9d9fe11955795f850e25ab95a23bd85b341b1b51d5ad9018e60b" } } ], "extra": [ 1, 65, 132, 153, 4, 54, 255, 215, 15, 5, 63, 132, 220, 44, 23, 248, 211, 87, 224, 144, 49, 47, 36, 138, 95, 85, 237, 140, 114, 5, 57, 27, 122, 2, 17, 0, 0, 0, 4, 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