Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 035657a65f1d9743622221408bdcb8d8c4a1a99e3d7e9bf47142170e0f185f5f

Tx prefix hash: 2bf942fcd2a23775f672f3eae7b456d4defd3ce70499f2fc94e3f26f9bbd6a96
Tx public key: 8719f0a19861a5cdd77e815c41800019e8a8edcdc8c5339011edfd3ef19a115d
Timestamp: 1729051939 Timestamp [UCT]: 2024-10-16 04:12:19 Age [y:d:h:m:s]: 01:028:08:12:31
Block: 1132619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278607 RingCT/type: yes/0
Extra: 018719f0a19861a5cdd77e815c41800019e8a8edcdc8c5339011edfd3ef19a115d0211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a7d7339f30834e63a56473d251d77e8af68539382628fc85227fffc81b27a73 0.600000000000 1615576 of 15

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": 1132629, "vin": [ { "gen": { "height": 1132619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7d7339f30834e63a56473d251d77e8af68539382628fc85227fffc81b27a73" } } ], "extra": [ 1, 135, 25, 240, 161, 152, 97, 165, 205, 215, 126, 129, 92, 65, 128, 0, 25, 232, 168, 237, 205, 200, 197, 51, 144, 17, 237, 253, 62, 241, 154, 17, 93, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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