Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87259b1be556973da166c276dd1e1ec1d2f1c1f7bc01cec09084778e462ee6c7

Tx prefix hash: 8fab608068af5c477333c89bc2c506c6c2f2694d83c7490575c4cad31df45de6
Tx public key: 1d803ae893a41b09d72d7585a6188f3b4c5d904b5cdfd0a63d9d701039dd6189
Timestamp: 1673768472 Timestamp [UCT]: 2023-01-15 07:41:12 Age [y:d:h:m:s]: 02:109:02:44:22
Block: 675123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599684 RingCT/type: yes/0
Extra: 011d803ae893a41b09d72d7585a6188f3b4c5d904b5cdfd0a63d9d701039dd61890211000000038b7b6602000000000000000000

1 output(s) for total of 3.556617768000 dcy

stealth address amount amount idx
00: 47a9626a8ea925e2c8fb0d3cfa8916becc8889717778bcae8e77f92f3e8ccb85 3.556617768000 1116794 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": 675133, "vin": [ { "gen": { "height": 675123 } } ], "vout": [ { "amount": 3556617768, "target": { "key": "47a9626a8ea925e2c8fb0d3cfa8916becc8889717778bcae8e77f92f3e8ccb85" } } ], "extra": [ 1, 29, 128, 58, 232, 147, 164, 27, 9, 215, 45, 117, 133, 166, 24, 143, 59, 76, 93, 144, 75, 92, 223, 208, 166, 61, 157, 112, 16, 57, 221, 97, 137, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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