Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae5b4cb0369e52ec14c4d346285a32583eb64aa68215954f3d4fc40450de021

Tx prefix hash: 93ef2b035326dda0f0a079eb760af168b4b23e788a18d3d9f5b1bd113a47ac13
Tx public key: 0a72313026d53457f8fb6a10af8f4074e3a120e10b705e5568059884c1005a90
Timestamp: 1722098470 Timestamp [UCT]: 2024-07-27 16:41:10 Age [y:d:h:m:s]: 00:264:16:24:04
Block: 1074952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189087 RingCT/type: yes/0
Extra: 010a72313026d53457f8fb6a10af8f4074e3a120e10b705e5568059884c1005a9002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5ebc858823d31f8a76bfc793717362630e01beb09d7b6eae9a9db16fdcdb508 0.600000000000 1547471 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": 1074962, "vin": [ { "gen": { "height": 1074952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5ebc858823d31f8a76bfc793717362630e01beb09d7b6eae9a9db16fdcdb508" } } ], "extra": [ 1, 10, 114, 49, 48, 38, 213, 52, 87, 248, 251, 106, 16, 175, 143, 64, 116, 227, 161, 32, 225, 11, 112, 94, 85, 104, 5, 152, 132, 193, 0, 90, 144, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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