Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cc9ef2f050b6ff70f1774500691d16c3b1111177a2e0fc7b3c182e359ee7be3

Tx prefix hash: 38dec8f367688b4d65d01dea3da1e5995a0ba41140d6dd3137606139e4fbe991
Tx public key: eb87700e1844f0ede75a2e4a39d4f080e3b7796401beb52add694f1a4b5eb83b
Timestamp: 1710040081 Timestamp [UCT]: 2024-03-10 03:08:01 Age [y:d:h:m:s]: 00:246:02:43:59
Block: 974994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176183 RingCT/type: yes/0
Extra: 01eb87700e1844f0ede75a2e4a39d4f080e3b7796401beb52add694f1a4b5eb83b02110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25612fe0f9b5cc975f36710cf0c4753445f7ade549199ca35979beb85fdf7cf3 0.600000000000 1434963 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": 975004, "vin": [ { "gen": { "height": 974994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25612fe0f9b5cc975f36710cf0c4753445f7ade549199ca35979beb85fdf7cf3" } } ], "extra": [ 1, 235, 135, 112, 14, 24, 68, 240, 237, 231, 90, 46, 74, 57, 212, 240, 128, 227, 183, 121, 100, 1, 190, 181, 42, 221, 105, 79, 26, 75, 94, 184, 59, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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