Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50c3c9787cc555f88650c3c133dc895dd5df483a0293c7dba37f7480063ed31

Tx prefix hash: 2c6a39e2817b6e6f1836af28228229546ec4445fa5e63a6eef4d141c458ab3e1
Tx public key: b2b3e268a397cfb7b64701f61d73bba2b3154e99c4be9314e5f1c6a389f54d4e
Timestamp: 1734549271 Timestamp [UCT]: 2024-12-18 19:14:31 Age [y:d:h:m:s]: 00:325:01:32:59
Block: 1178091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229803 RingCT/type: yes/0
Extra: 01b2b3e268a397cfb7b64701f61d73bba2b3154e99c4be9314e5f1c6a389f54d4e021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0817a14bab558e160862f3a617763b7c8505e8a90bd07f0e6c8088ed805acae0 0.600000000000 1664474 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": 1178101, "vin": [ { "gen": { "height": 1178091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0817a14bab558e160862f3a617763b7c8505e8a90bd07f0e6c8088ed805acae0" } } ], "extra": [ 1, 178, 179, 226, 104, 163, 151, 207, 183, 182, 71, 1, 246, 29, 115, 187, 162, 179, 21, 78, 153, 196, 190, 147, 20, 229, 241, 198, 163, 137, 245, 77, 78, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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