Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c397616b76727f71c4aaf3f089f194c08dde1811bc85ae8037296a6312376bd0

Tx prefix hash: bb6e6aefec81e003680da653fb589c1a5a2ca2ee8997ef63265b88ffc7aae569
Tx public key: d8b0fcf5e0bf0b2a5793719315ac723cd08c5dd45f6459356601ed787e77f222
Timestamp: 1728374149 Timestamp [UCT]: 2024-10-08 07:55:49 Age [y:d:h:m:s]: 00:250:05:03:04
Block: 1126983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178559 RingCT/type: yes/0
Extra: 01d8b0fcf5e0bf0b2a5793719315ac723cd08c5dd45f6459356601ed787e77f222021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0a49c4e08e2e3e1f2c3525c0a326164d6e6b6a51a4f9b192aa8d414c5b08176 0.600000000000 1609782 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": 1126993, "vin": [ { "gen": { "height": 1126983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0a49c4e08e2e3e1f2c3525c0a326164d6e6b6a51a4f9b192aa8d414c5b08176" } } ], "extra": [ 1, 216, 176, 252, 245, 224, 191, 11, 42, 87, 147, 113, 147, 21, 172, 114, 60, 208, 140, 93, 212, 95, 100, 89, 53, 102, 1, 237, 120, 126, 119, 242, 34, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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