Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b2488e1d5cada92869f823792f9391ca595f83a3e7a5338bc1def9930ca29fc

Tx prefix hash: bf6d30048a68d7e606a75b63f008ee96e622007a0fbb214da04477330ff6578f
Tx public key: bdd68ad6a02c51610136e4a10b3b3b4a81cc8b0dd2f34a76c5690f026c137e85
Timestamp: 1729523981 Timestamp [UCT]: 2024-10-21 15:19:41 Age [y:d:h:m:s]: 00:078:05:25:23
Block: 1136475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55935 RingCT/type: yes/0
Extra: 01bdd68ad6a02c51610136e4a10b3b3b4a81cc8b0dd2f34a76c5690f026c137e85021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43874b02b9a28f1ac31350bc9405a493f76cf3fe4345d0e005027170c186ec86 0.600000000000 1619820 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": 1136485, "vin": [ { "gen": { "height": 1136475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43874b02b9a28f1ac31350bc9405a493f76cf3fe4345d0e005027170c186ec86" } } ], "extra": [ 1, 189, 214, 138, 214, 160, 44, 81, 97, 1, 54, 228, 161, 11, 59, 59, 74, 129, 204, 139, 13, 210, 243, 74, 118, 197, 105, 15, 2, 108, 19, 126, 133, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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