Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35c7d377ca46cf794934aa9b0f2746a79fd1ac6a8e36ce678b707a0273d215c6

Tx prefix hash: b5d2231e01b722f63afe54fc95d0fcf76246e526f2f384205474d6b09c28b492
Tx public key: a84b9c81f4d4fe60e2df2a23b9e1b8f0749d9a03b8e1822b554f676bce8b1179
Timestamp: 1709461987 Timestamp [UCT]: 2024-03-03 10:33:07 Age [y:d:h:m:s]: 01:065:20:31:24
Block: 970188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308094 RingCT/type: yes/0
Extra: 01a84b9c81f4d4fe60e2df2a23b9e1b8f0749d9a03b8e1822b554f676bce8b117902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2239e5dada6bed4062c6cd27745a5a5655092044ccf3c4ee6a9fe79c0b8d8b20 0.600000000000 1430037 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": 970198, "vin": [ { "gen": { "height": 970188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2239e5dada6bed4062c6cd27745a5a5655092044ccf3c4ee6a9fe79c0b8d8b20" } } ], "extra": [ 1, 168, 75, 156, 129, 244, 212, 254, 96, 226, 223, 42, 35, 185, 225, 184, 240, 116, 157, 154, 3, 184, 225, 130, 43, 85, 79, 103, 107, 206, 139, 17, 121, 2, 17, 0, 0, 0, 5, 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