Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9346837e42cbe78921bfbb5be013d97df392c166a49d8a33d9978a6c3c021f13

Tx prefix hash: 633eb42926af4aedca63cb80c4f4128c7fe20cd0b55ad3c63d1d8b52cad52e7e
Tx public key: 2e9cc4db83dfe0cc612232fbd4bfb9417623c38a957bac0708c203b4c5ebb3b3
Timestamp: 1705549746 Timestamp [UCT]: 2024-01-18 03:49:06 Age [y:d:h:m:s]: 01:086:17:14:42
Block: 937727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323095 RingCT/type: yes/0
Extra: 012e9cc4db83dfe0cc612232fbd4bfb9417623c38a957bac0708c203b4c5ebb3b30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd247166d04f7a37bd8d71e5dca6e6cf71dcf59ebc75641abcbb88d750c7b91 0.600000000000 1395789 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": 937737, "vin": [ { "gen": { "height": 937727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd247166d04f7a37bd8d71e5dca6e6cf71dcf59ebc75641abcbb88d750c7b91" } } ], "extra": [ 1, 46, 156, 196, 219, 131, 223, 224, 204, 97, 34, 50, 251, 212, 191, 185, 65, 118, 35, 195, 138, 149, 123, 172, 7, 8, 194, 3, 180, 197, 235, 179, 179, 2, 17, 0, 0, 0, 1, 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