Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d774875223026ef5df85c5cfc6ac0497cafbf8fc81f8955ce1a34984ec396f5

Tx prefix hash: 071fa72f25f9350f5fb3b6061c088ed7c8da88a8c5bba011c2c82979f284c013
Tx public key: 22018b1d02f853f803a8d61be77fe6973abddf7bd626a5e14af38fbd4f368a45
Timestamp: 1710090217 Timestamp [UCT]: 2024-03-10 17:03:37 Age [y:d:h:m:s]: 00:228:23:21:35
Block: 975410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163963 RingCT/type: yes/0
Extra: 0122018b1d02f853f803a8d61be77fe6973abddf7bd626a5e14af38fbd4f368a45021100000002b757f2ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38bdd7918878c78dba39cc00b364befac6f82d8dc8a9c8416c7a55084ec8db02 0.600000000000 1435381 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": 975420, "vin": [ { "gen": { "height": 975410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38bdd7918878c78dba39cc00b364befac6f82d8dc8a9c8416c7a55084ec8db02" } } ], "extra": [ 1, 34, 1, 139, 29, 2, 248, 83, 248, 3, 168, 214, 27, 231, 127, 230, 151, 58, 189, 223, 123, 214, 38, 165, 225, 74, 243, 143, 189, 79, 54, 138, 69, 2, 17, 0, 0, 0, 2, 183, 87, 242, 172, 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