Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02af738bcd7000057483f997b4b3394357afda2f0b990c32c28b2583a0265203

Tx prefix hash: 9da7960c0a6e0e3ebb3b1a9b280420d2f496a30ae16fe5ae3d5d0daa1f1186ee
Tx public key: 16e52584aa53a4e9280e511fdd7da02121e8d8459a4317c78b2c173310312d23
Timestamp: 1688217065 Timestamp [UCT]: 2023-07-01 13:11:05 Age [y:d:h:m:s]: 01:243:06:54:37
Block: 794323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434989 RingCT/type: yes/0
Extra: 0116e52584aa53a4e9280e511fdd7da02121e8d8459a4317c78b2c173310312d230211000000024b8f5122000000000000000000

1 output(s) for total of 1.432446135000 dcy

stealth address amount amount idx
00: 96304a59bd898650bf324d0dfd4cec2937ded4bdd09bf415428e0a53db09d984 1.432446135000 1245062 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": 794333, "vin": [ { "gen": { "height": 794323 } } ], "vout": [ { "amount": 1432446135, "target": { "key": "96304a59bd898650bf324d0dfd4cec2937ded4bdd09bf415428e0a53db09d984" } } ], "extra": [ 1, 22, 229, 37, 132, 170, 83, 164, 233, 40, 14, 81, 31, 221, 125, 160, 33, 33, 232, 216, 69, 154, 67, 23, 199, 139, 44, 23, 51, 16, 49, 45, 35, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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