Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 317b62ebf51e95b2c06d605444d807a3af855e03f4d48e2408d3549120c5076d

Tx prefix hash: 76c350ec9eb7445a6df8e0e81e30dfded0503d39a5c233e5b18c41fcef6b27d7
Tx public key: 8d823d88d7329fd60cdf1ed72d0060f459efe3a21e88c2eb57ddaa5dbbdacd18
Timestamp: 1704131082 Timestamp [UCT]: 2024-01-01 17:44:42 Age [y:d:h:m:s]: 01:165:18:57:51
Block: 925989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379547 RingCT/type: yes/0
Extra: 018d823d88d7329fd60cdf1ed72d0060f459efe3a21e88c2eb57ddaa5dbbdacd180211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f54e038e545eb58cfc0e416ca1f78c73313ea3a8f56b089118847b58de8af810 0.600000000000 1383759 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": 925999, "vin": [ { "gen": { "height": 925989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f54e038e545eb58cfc0e416ca1f78c73313ea3a8f56b089118847b58de8af810" } } ], "extra": [ 1, 141, 130, 61, 136, 215, 50, 159, 214, 12, 223, 30, 215, 45, 0, 96, 244, 89, 239, 227, 162, 30, 136, 194, 235, 87, 221, 170, 93, 187, 218, 205, 24, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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