Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f67bc2179af27adcb007e3c036be3ef9e2289aef841d64c34e519f900d785ba1

Tx prefix hash: 8fcdd723f9cf3b2a56cb30dc8d500c1767b118f755f0b834d84cefaf3aef45d6
Tx public key: ddd86b75fc25f08f4d403a6a109bb8de0cc2e4c12bc3b89aa1aecffc031959d5
Timestamp: 1672605158 Timestamp [UCT]: 2023-01-01 20:32:38 Age [y:d:h:m:s]: 02:054:21:27:47
Block: 665493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560889 RingCT/type: yes/0
Extra: 01ddd86b75fc25f08f4d403a6a109bb8de0cc2e4c12bc3b89aa1aecffc031959d502110000000975e3f0e9000000000000000000

1 output(s) for total of 3.827766133000 dcy

stealth address amount amount idx
00: 3099f6b810fc118ecb16e1ff25c057d4b96dd807d82e0a5f0426998ae1bed6c3 3.827766133000 1106540 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": 665503, "vin": [ { "gen": { "height": 665493 } } ], "vout": [ { "amount": 3827766133, "target": { "key": "3099f6b810fc118ecb16e1ff25c057d4b96dd807d82e0a5f0426998ae1bed6c3" } } ], "extra": [ 1, 221, 216, 107, 117, 252, 37, 240, 143, 77, 64, 58, 106, 16, 155, 184, 222, 12, 194, 228, 193, 43, 195, 184, 154, 161, 174, 207, 252, 3, 25, 89, 213, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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