Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dce209fb9f984ffacda02576d1a9cfebe4b703ae7be9a24095b05fda6b219cf

Tx prefix hash: 4045e64284b52f13260aac8328c55589f056ea839ef409e6a50bc0e7c8f5bbd3
Tx public key: 36869e13fb1bb5c9ca8b30da10eb11da6743922680f61dc830a800bb97964cd6
Timestamp: 1723948975 Timestamp [UCT]: 2024-08-18 02:42:55 Age [y:d:h:m:s]: 00:235:00:33:58
Block: 1090300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167842 RingCT/type: yes/0
Extra: 0136869e13fb1bb5c9ca8b30da10eb11da6743922680f61dc830a800bb97964cd6021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c92f4badb6bf6b77a1b4a42d4500a649410bb655f616cbe4ad1a2e63021ee3f 0.600000000000 1564923 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": 1090310, "vin": [ { "gen": { "height": 1090300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c92f4badb6bf6b77a1b4a42d4500a649410bb655f616cbe4ad1a2e63021ee3f" } } ], "extra": [ 1, 54, 134, 158, 19, 251, 27, 181, 201, 202, 139, 48, 218, 16, 235, 17, 218, 103, 67, 146, 38, 128, 246, 29, 200, 48, 168, 0, 187, 151, 150, 76, 214, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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