Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0412efd80dbcbc50e256d88889fb0e4b778dce83d63b6fb4a679dea6d0cd03a0

Tx prefix hash: df3a42b548190a98b4d83dbcf71f45e6d8c209924a1be25bebd10fa40cc75b58
Tx public key: f227ff70c2f2ff4be7b11249c39cd56ee9409502d41bf630c81302eb9d8b2964
Timestamp: 1705543174 Timestamp [UCT]: 2024-01-18 01:59:34 Age [y:d:h:m:s]: 01:084:15:10:06
Block: 937668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321596 RingCT/type: yes/0
Extra: 01f227ff70c2f2ff4be7b11249c39cd56ee9409502d41bf630c81302eb9d8b29640211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5892bb96356565182f7e17291b9ac740f0d7b2df39f8d544742c1f9a2a45e86a 0.600000000000 1395730 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": 937678, "vin": [ { "gen": { "height": 937668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5892bb96356565182f7e17291b9ac740f0d7b2df39f8d544742c1f9a2a45e86a" } } ], "extra": [ 1, 242, 39, 255, 112, 194, 242, 255, 75, 231, 177, 18, 73, 195, 156, 213, 110, 233, 64, 149, 2, 212, 27, 246, 48, 200, 19, 2, 235, 157, 139, 41, 100, 2, 17, 0, 0, 0, 2, 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