Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a27cb3f59ac68551e3e548c05a57978a58079536e5e68b3a280bda4a102ef52c

Tx prefix hash: 7fc20a60f3f13c3e0c35d7d606956101218a2a86e99aa5576b082067ddce8549
Tx public key: 4329e832eba41f892980a655078d65f48e8a2a423754da39abae524a7f4def94
Timestamp: 1720240667 Timestamp [UCT]: 2024-07-06 04:37:47 Age [y:d:h:m:s]: 00:343:18:11:05
Block: 1059541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245595 RingCT/type: yes/0
Extra: 014329e832eba41f892980a655078d65f48e8a2a423754da39abae524a7f4def9402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97c686270c3d04438b6ba242d5afef72730a7c496337ca42c7ef3d68c97f07df 0.600000000000 1530010 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": 1059551, "vin": [ { "gen": { "height": 1059541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97c686270c3d04438b6ba242d5afef72730a7c496337ca42c7ef3d68c97f07df" } } ], "extra": [ 1, 67, 41, 232, 50, 235, 164, 31, 137, 41, 128, 166, 85, 7, 141, 101, 244, 142, 138, 42, 66, 55, 84, 218, 57, 171, 174, 82, 74, 127, 77, 239, 148, 2, 17, 0, 0, 0, 3, 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