Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf2055d86e6e83b1da197676a224b89599e4bd5854f1ea10c3068b8f9f55c7b

Tx prefix hash: 6663e4f5fd578f8e5d4a87ea8ddcd8d19616efc146bbdeb0236e2438e7bf440a
Tx public key: 168f3745096cd2175c4364c9d7974d8702e5381989d17fe5d4dcaef3ef5b1d7e
Timestamp: 1697840253 Timestamp [UCT]: 2023-10-20 22:17:33 Age [y:d:h:m:s]: 01:159:19:48:10
Block: 874047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375236 RingCT/type: yes/0
Extra: 01168f3745096cd2175c4364c9d7974d8702e5381989d17fe5d4dcaef3ef5b1d7e02110000000133af99f4000000000000000000

1 output(s) for total of 0.779685533000 dcy

stealth address amount amount idx
00: c7f10067462ef7a935376eef039e102fdc18185d10c779b5aa23ae8967659630 0.779685533000 1329241 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": 874057, "vin": [ { "gen": { "height": 874047 } } ], "vout": [ { "amount": 779685533, "target": { "key": "c7f10067462ef7a935376eef039e102fdc18185d10c779b5aa23ae8967659630" } } ], "extra": [ 1, 22, 143, 55, 69, 9, 108, 210, 23, 92, 67, 100, 201, 215, 151, 77, 135, 2, 229, 56, 25, 137, 209, 127, 229, 212, 220, 174, 243, 239, 91, 29, 126, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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