Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60c09812d846198c925e1b85129eb46dcc63065b0cf18b14102934c971f0ddb1

Tx prefix hash: 0e1233783ad33c6029c8634e6d7fccf27260d3f106a6ed06cd3c21f0cea8db47
Tx public key: 1a36588a093756b40d4aadbbb72b03841236d1a7ac832c7e40d93917a6c30245
Timestamp: 1720841245 Timestamp [UCT]: 2024-07-13 03:27:25 Age [y:d:h:m:s]: 00:271:12:10:38
Block: 1064540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193968 RingCT/type: yes/0
Extra: 011a36588a093756b40d4aadbbb72b03841236d1a7ac832c7e40d93917a6c3024502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6da3e479ae0edddf35f587f6798a7e106fe5e54bd67e3e6af737541218b4eb1 0.600000000000 1535069 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": 1064550, "vin": [ { "gen": { "height": 1064540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6da3e479ae0edddf35f587f6798a7e106fe5e54bd67e3e6af737541218b4eb1" } } ], "extra": [ 1, 26, 54, 88, 138, 9, 55, 86, 180, 13, 74, 173, 187, 183, 43, 3, 132, 18, 54, 209, 167, 172, 131, 44, 126, 64, 217, 57, 23, 166, 195, 2, 69, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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