Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21c40184de824debb8ff3e92a5cfda01ce3e293bc077c18a159e29176dd65b8b

Tx prefix hash: 682f358d1e2b2e733c933db593b0415fe7ac5b4f910c6b3e885ed3d767ee5be3
Tx public key: a4fd52f2f05fcf77ca0796285e88cc8de5fab22a01d4f4a9e1f236d1d37f5c5c
Timestamp: 1705645482 Timestamp [UCT]: 2024-01-19 06:24:42 Age [y:d:h:m:s]: 01:080:02:21:15
Block: 938530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318330 RingCT/type: yes/0
Extra: 01a4fd52f2f05fcf77ca0796285e88cc8de5fab22a01d4f4a9e1f236d1d37f5c5c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3e15d3a45736999797b2a6e098ed5f1d891afc1ad928e96620069960a6bad35 0.600000000000 1396600 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": 938540, "vin": [ { "gen": { "height": 938530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3e15d3a45736999797b2a6e098ed5f1d891afc1ad928e96620069960a6bad35" } } ], "extra": [ 1, 164, 253, 82, 242, 240, 95, 207, 119, 202, 7, 150, 40, 94, 136, 204, 141, 229, 250, 178, 42, 1, 212, 244, 169, 225, 242, 54, 209, 211, 127, 92, 92, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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