Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f759213792aeeff5643aa412e393dc4f854e3a0227cb179526974b15b2c27a5

Tx prefix hash: 25d89b591cc98c23be6ee7012563bbfd3e0d020258cf82a0d3e0dd8905351874
Tx public key: 8db7eca959105bbb9c462e7fda68e618b795c4193b333f6416505e829e2e292a
Timestamp: 1717209237 Timestamp [UCT]: 2024-06-01 02:33:57 Age [y:d:h:m:s]: 00:240:14:25:06
Block: 1034422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171945 RingCT/type: yes/0
Extra: 018db7eca959105bbb9c462e7fda68e618b795c4193b333f6416505e829e2e292a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7f624bd4a7f9083e4aa9a40d2956251b0fddd1f5cf278f2ef9ba9aa37346791 0.600000000000 1502935 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": 1034432, "vin": [ { "gen": { "height": 1034422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7f624bd4a7f9083e4aa9a40d2956251b0fddd1f5cf278f2ef9ba9aa37346791" } } ], "extra": [ 1, 141, 183, 236, 169, 89, 16, 91, 187, 156, 70, 46, 127, 218, 104, 230, 24, 183, 149, 196, 25, 59, 51, 63, 100, 22, 80, 94, 130, 158, 46, 41, 42, 2, 17, 0, 0, 0, 5, 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