Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 176fad92f2429b447c38bf5379e7339b4b3fbfdbe371ea1f0259952617209e48

Tx prefix hash: 9c1f5282ffb4a3ead23e7161e3bcb58121960bc964547af76e7d2da9309857fd
Tx public key: 15546f7e89f325ae0019a5cbf2f0c00423515c2b91868cc29d6450ea9c549e42
Timestamp: 1722491841 Timestamp [UCT]: 2024-08-01 05:57:21 Age [y:d:h:m:s]: 00:301:03:28:33
Block: 1078211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215186 RingCT/type: yes/0
Extra: 0115546f7e89f325ae0019a5cbf2f0c00423515c2b91868cc29d6450ea9c549e42021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c66052597450e6d8bd72e1a71a74c925d1a17a85e1e76a66f737e67bb50e2982 0.600000000000 1550780 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": 1078221, "vin": [ { "gen": { "height": 1078211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c66052597450e6d8bd72e1a71a74c925d1a17a85e1e76a66f737e67bb50e2982" } } ], "extra": [ 1, 21, 84, 111, 126, 137, 243, 37, 174, 0, 25, 165, 203, 242, 240, 192, 4, 35, 81, 92, 43, 145, 134, 140, 194, 157, 100, 80, 234, 156, 84, 158, 66, 2, 17, 0, 0, 0, 4, 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