Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e411d1dd4cd90324b9889f07eab3b0299f6101765d395fbf4343c917e93de19

Tx prefix hash: a9ed15cdf6bd971bd685e40c4919dc586932361999e67130d9b3a0ee4393d3c8
Tx public key: a38e15f7c3c1455ef394f68de9d90b690dd7d3a733810f6728ec3aa37c68f2b0
Timestamp: 1716411085 Timestamp [UCT]: 2024-05-22 20:51:25 Age [y:d:h:m:s]: 00:305:15:33:33
Block: 1027794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218457 RingCT/type: yes/0
Extra: 01a38e15f7c3c1455ef394f68de9d90b690dd7d3a733810f6728ec3aa37c68f2b00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d78d95abae352b57c9277f8e35f8070ebfd7712430792ed654eee84624ddc59e 0.600000000000 1495611 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": 1027804, "vin": [ { "gen": { "height": 1027794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d78d95abae352b57c9277f8e35f8070ebfd7712430792ed654eee84624ddc59e" } } ], "extra": [ 1, 163, 142, 21, 247, 195, 193, 69, 94, 243, 148, 246, 141, 233, 217, 11, 105, 13, 215, 211, 167, 51, 129, 15, 103, 40, 236, 58, 163, 124, 104, 242, 176, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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