Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67f83a829ff4a0098d932b49880adad0b7a8e09211c7d3d546555ed05e2ed0d6

Tx prefix hash: 3d8d11b4d5fcd6f81588d3b99c03b70d3a990496fb8ab46293535569cc494218
Tx public key: b3d870e573f13a902d229ea4d64751eb41ca4f19105459e7d8bf98c0883c077b
Timestamp: 1655256330 Timestamp [UCT]: 2022-06-15 01:25:30 Age [y:d:h:m:s]: 02:335:02:05:06
Block: 522604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 760578 RingCT/type: yes/0
Extra: 01b3d870e573f13a902d229ea4d64751eb41ca4f19105459e7d8bf98c0883c077b02110000000375e3f0e9000000000000000000

1 output(s) for total of 11.386655389000 dcy

stealth address amount amount idx
00: 16dd697e87422c2d124117aa081e84e512d12e9433426658225ec33222e38e4e 11.386655389000 950647 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": 522614, "vin": [ { "gen": { "height": 522604 } } ], "vout": [ { "amount": 11386655389, "target": { "key": "16dd697e87422c2d124117aa081e84e512d12e9433426658225ec33222e38e4e" } } ], "extra": [ 1, 179, 216, 112, 229, 115, 241, 58, 144, 45, 34, 158, 164, 214, 71, 81, 235, 65, 202, 79, 25, 16, 84, 89, 231, 216, 191, 152, 192, 136, 60, 7, 123, 2, 17, 0, 0, 0, 3, 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