Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a95973d062ca2957f02ed647255cd6bee1a2dbe621dc030f8e983c36a34c20a9

Tx prefix hash: 7a313f3c6a8687d9d7f90f742673d8baeac5754f5857748ba0c66534a06f4b2e
Tx public key: 909bfa1da7815f0e0e827140332663f85f33ed5269554dbcde0dcee5507c11a1
Timestamp: 1673580821 Timestamp [UCT]: 2023-01-13 03:33:41 Age [y:d:h:m:s]: 02:324:19:50:19
Block: 673590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 751572 RingCT/type: yes/0
Extra: 01909bfa1da7815f0e0e827140332663f85f33ed5269554dbcde0dcee5507c11a102110000000675e3f0e9000000000000000000

1 output(s) for total of 3.598459851000 dcy

stealth address amount amount idx
00: 0b7521afc0191dc23f841f1a3d0d0e0a2ea5eb37f4d6a3e0bd83915c54f266b7 3.598459851000 1115205 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": 673600, "vin": [ { "gen": { "height": 673590 } } ], "vout": [ { "amount": 3598459851, "target": { "key": "0b7521afc0191dc23f841f1a3d0d0e0a2ea5eb37f4d6a3e0bd83915c54f266b7" } } ], "extra": [ 1, 144, 155, 250, 29, 167, 129, 95, 14, 14, 130, 113, 64, 51, 38, 99, 248, 95, 51, 237, 82, 105, 85, 77, 188, 222, 13, 206, 229, 80, 124, 17, 161, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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