Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92ae5f06599623a1a8c4edf65873163c4543c3f151fd01160e6470e77d6258a3

Tx prefix hash: f0c591df873fc780b0a27ae959264a6f11eab5841e6e724f1d59a09348926e22
Tx public key: 2ff2108f7f4f7b7908464f55e8989c9887e18cdb30333fd44652a1ceacd649db
Timestamp: 1696890333 Timestamp [UCT]: 2023-10-09 22:25:33 Age [y:d:h:m:s]: 01:176:10:00:15
Block: 866170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387112 RingCT/type: yes/0
Extra: 012ff2108f7f4f7b7908464f55e8989c9887e18cdb30333fd44652a1ceacd649db02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.828018879000 dcy

stealth address amount amount idx
00: d06b57df24f8964eed52a329773f4250675f8c62e130dd9c4e307159d8709f60 0.828018879000 1320742 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": 866180, "vin": [ { "gen": { "height": 866170 } } ], "vout": [ { "amount": 828018879, "target": { "key": "d06b57df24f8964eed52a329773f4250675f8c62e130dd9c4e307159d8709f60" } } ], "extra": [ 1, 47, 242, 16, 143, 127, 79, 123, 121, 8, 70, 79, 85, 232, 152, 156, 152, 135, 225, 140, 219, 48, 51, 63, 212, 70, 82, 161, 206, 172, 214, 73, 219, 2, 17, 0, 0, 0, 7, 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