Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3917cac72e036e596c11cb6450b74568d2ea5ab2c15400adb151386d1a218d7f

Tx prefix hash: 567594061867da7252a45fd80807cfc8c78506bfccd978113ead4761440619ef
Tx public key: dbd07e2a73dab5a3a1e0515e67ba7c1e6835816b7b85041e885605b84dd4eac7
Timestamp: 1695524885 Timestamp [UCT]: 2023-09-24 03:08:05 Age [y:d:h:m:s]: 01:264:07:08:04
Block: 854844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449936 RingCT/type: yes/0
Extra: 01dbd07e2a73dab5a3a1e0515e67ba7c1e6835816b7b85041e885605b84dd4eac7021100000010e6d27f9c000000000000000000

1 output(s) for total of 0.902707426000 dcy

stealth address amount amount idx
00: 50d6ed7eab66e8f43e3af64729e8ce274f45c95565823b240a5461fb3aaf3b8d 0.902707426000 1308836 of 0

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": 854854, "vin": [ { "gen": { "height": 854844 } } ], "vout": [ { "amount": 902707426, "target": { "key": "50d6ed7eab66e8f43e3af64729e8ce274f45c95565823b240a5461fb3aaf3b8d" } } ], "extra": [ 1, 219, 208, 126, 42, 115, 218, 181, 163, 161, 224, 81, 94, 103, 186, 124, 30, 104, 53, 129, 107, 123, 133, 4, 30, 136, 86, 5, 184, 77, 212, 234, 199, 2, 17, 0, 0, 0, 16, 230, 210, 127, 156, 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