Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2515d1e23bac01aab5871c0b64bb0b1bff41ecc0b0f1e3dd136ec1137198a68

Tx prefix hash: 0a57e9b77b09e0999fefb968a8a47c6c581ca3325e613f96c0a036ceccf5b285
Tx public key: c408283a1d835688772ee8db1f28f1f5c515dcd5c531c19fe4c52aadbacfbb2e
Timestamp: 1694744911 Timestamp [UCT]: 2023-09-15 02:28:31 Age [y:d:h:m:s]: 01:133:18:28:39
Block: 848358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356892 RingCT/type: yes/0
Extra: 01c408283a1d835688772ee8db1f28f1f5c515dcd5c531c19fe4c52aadbacfbb2e02110000000133af99f4000000000000000000

1 output(s) for total of 0.948541091000 dcy

stealth address amount amount idx
00: 53ad16e77080a4a36762be806510b895c72db7369a6035b055eaeab405bcd117 0.948541091000 1301954 of 0

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": 848368, "vin": [ { "gen": { "height": 848358 } } ], "vout": [ { "amount": 948541091, "target": { "key": "53ad16e77080a4a36762be806510b895c72db7369a6035b055eaeab405bcd117" } } ], "extra": [ 1, 196, 8, 40, 58, 29, 131, 86, 136, 119, 46, 232, 219, 31, 40, 241, 245, 197, 21, 220, 213, 197, 49, 193, 159, 228, 197, 42, 173, 186, 207, 187, 46, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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