Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c136e4c1bab7a0262076c7b851990f3feb508dff4ad8ab3ca7de615bc958ada

Tx prefix hash: ebece966456e09a8b68933c79177eccd6ca6c095471f322f51d8b8f74e6775f3
Tx public key: 3d4159738ac667c1d2309b62f5839be62809c6e9453c4b6f55a4b7a6a5597eed
Timestamp: 1713124054 Timestamp [UCT]: 2024-04-14 19:47:34 Age [y:d:h:m:s]: 01:199:07:03:04
Block: 1000528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401113 RingCT/type: yes/0
Extra: 013d4159738ac667c1d2309b62f5839be62809c6e9453c4b6f55a4b7a6a5597eed02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 558631d25c34116b5867201d6f5bc03b131bf0eeeafc1a8ef79dec777d351cfd 0.600000000000 1461026 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": 1000538, "vin": [ { "gen": { "height": 1000528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "558631d25c34116b5867201d6f5bc03b131bf0eeeafc1a8ef79dec777d351cfd" } } ], "extra": [ 1, 61, 65, 89, 115, 138, 198, 103, 193, 210, 48, 155, 98, 245, 131, 155, 230, 40, 9, 198, 233, 69, 60, 75, 111, 85, 164, 183, 166, 165, 89, 126, 237, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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