Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6052c40bd04145ea3585dca20f20bb1e99a54b5caa003b72b998813635e7459

Tx prefix hash: 88c3da75134be75956d07f08812436731d627760c1d38d2f54222fbcc962f647
Tx public key: 3bfaff4cb7bad2c1af1849e393f8bde99dcd9f122582062c435872f1c41bdc6f
Timestamp: 1695604678 Timestamp [UCT]: 2023-09-25 01:17:58 Age [y:d:h:m:s]: 01:136:14:18:45
Block: 855506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358670 RingCT/type: yes/0
Extra: 013bfaff4cb7bad2c1af1849e393f8bde99dcd9f122582062c435872f1c41bdc6f021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.898159635000 dcy

stealth address amount amount idx
00: 05853bd7acb18fbe6e23c71f500da42c8bd06dce798b62961d386c024d6d22f7 0.898159635000 1309530 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": 855516, "vin": [ { "gen": { "height": 855506 } } ], "vout": [ { "amount": 898159635, "target": { "key": "05853bd7acb18fbe6e23c71f500da42c8bd06dce798b62961d386c024d6d22f7" } } ], "extra": [ 1, 59, 250, 255, 76, 183, 186, 210, 193, 175, 24, 73, 227, 147, 248, 189, 233, 157, 205, 159, 18, 37, 130, 6, 44, 67, 88, 114, 241, 196, 27, 220, 111, 2, 17, 0, 0, 0, 9, 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