Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ebb38648290f7df8c9d41f42e9447ce6b51ec098d09c6d75f2848e538cbbd4

Tx prefix hash: f0fee47834754f1f9b267170d0bd722b290dbfa2fce45591cb4f7e9ed45831ba
Tx public key: 0ff88095db9406121741b66dcb3f32e450571c5bedb1f986d435e2283f0429a6
Timestamp: 1676854361 Timestamp [UCT]: 2023-02-20 00:52:41 Age [y:d:h:m:s]: 02:046:10:33:34
Block: 700735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554785 RingCT/type: yes/0
Extra: 010ff88095db9406121741b66dcb3f32e450571c5bedb1f986d435e2283f0429a602110000000174b6d784000000000000000000

1 output(s) for total of 2.925323960000 dcy

stealth address amount amount idx
00: a7806d0d16b74ea3ce22324dde648d6a23eaefa6bb0ae0a3c4f0ba97ec2dec2b 2.925323960000 1144186 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": 700745, "vin": [ { "gen": { "height": 700735 } } ], "vout": [ { "amount": 2925323960, "target": { "key": "a7806d0d16b74ea3ce22324dde648d6a23eaefa6bb0ae0a3c4f0ba97ec2dec2b" } } ], "extra": [ 1, 15, 248, 128, 149, 219, 148, 6, 18, 23, 65, 182, 109, 203, 63, 50, 228, 80, 87, 28, 91, 237, 177, 249, 134, 212, 53, 226, 40, 63, 4, 41, 166, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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