Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e14fe12fb102d9999a119d17f94c271deb1fab38f76f32cdd23b5a0fcf4bdb7

Tx prefix hash: 614e1e95b40debc18f6854f049bb74e5ae558cdf83f331cb02a07745c1dd2f2f
Tx public key: d6fc3f9de96f4187dd871e89f803c09e591cc2a2724838528f3c16b7f5ae7eaa
Timestamp: 1583752306 Timestamp [UCT]: 2020-03-09 11:11:46 Age [y:d:h:m:s]: 05:006:04:20:17
Block: 79286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1159927 RingCT/type: yes/0
Extra: 01d6fc3f9de96f4187dd871e89f803c09e591cc2a2724838528f3c16b7f5ae7eaa02110000003a6d997e00000000000000000000

1 output(s) for total of 335.191780033000 dcy

stealth address amount amount idx
00: 2aa88f10eb63ca7bd5819d962c507dec0464d23151175753100f27cfe55cf0b8 335.191780033000 145078 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": 79296, "vin": [ { "gen": { "height": 79286 } } ], "vout": [ { "amount": 335191780033, "target": { "key": "2aa88f10eb63ca7bd5819d962c507dec0464d23151175753100f27cfe55cf0b8" } } ], "extra": [ 1, 214, 252, 63, 157, 233, 111, 65, 135, 221, 135, 30, 137, 248, 3, 192, 158, 89, 28, 194, 162, 114, 72, 56, 82, 143, 60, 22, 183, 245, 174, 126, 170, 2, 17, 0, 0, 0, 58, 109, 153, 126, 0, 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