Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f63cdce08aa110d33ad0dfc6d27074b3b31c563ed5273b0e760b4c38a5029e5

Tx prefix hash: a206a612117f5af078ad2980ae5373fd17febb3ff7a4f3dcb4738e2a7992dc6f
Tx public key: 92a0c7b14a92559cf10396454ce773d0e8314e303927fbc7e2e8fd77aa97f148
Timestamp: 1717496865 Timestamp [UCT]: 2024-06-04 10:27:45 Age [y:d:h:m:s]: 00:306:06:17:38
Block: 1036813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218859 RingCT/type: yes/0
Extra: 0192a0c7b14a92559cf10396454ce773d0e8314e303927fbc7e2e8fd77aa97f1480211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d5beb19877d30ee7892dd6f52004069960447d61b9ee1eff635c464444e1f9 0.600000000000 1505342 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": 1036823, "vin": [ { "gen": { "height": 1036813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d5beb19877d30ee7892dd6f52004069960447d61b9ee1eff635c464444e1f9" } } ], "extra": [ 1, 146, 160, 199, 177, 74, 146, 85, 156, 241, 3, 150, 69, 76, 231, 115, 208, 232, 49, 78, 48, 57, 39, 251, 199, 226, 232, 253, 119, 170, 151, 241, 72, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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