Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb43957adc183a8a75268720979a58df18fa58546ab465f72d06a47acb99fdab

Tx prefix hash: 71a563de087d2d67579340714cd737b774e3ea48e3ba32b067ec23e059d5d425
Tx public key: 076ac96cbc9c4b2ce810919a2fa417543ad4b928ab282b478cb5ecfd0d068f0f
Timestamp: 1732242484 Timestamp [UCT]: 2024-11-22 02:28:04 Age [y:d:h:m:s]: 00:002:00:33:52
Block: 1158963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1443 RingCT/type: yes/0
Extra: 01076ac96cbc9c4b2ce810919a2fa417543ad4b928ab282b478cb5ecfd0d068f0f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31e658cd5092b28d1e19bb806d1d1bbd738dfc38e215802e812abe6a36669693 0.600000000000 1644594 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": 1158973, "vin": [ { "gen": { "height": 1158963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31e658cd5092b28d1e19bb806d1d1bbd738dfc38e215802e812abe6a36669693" } } ], "extra": [ 1, 7, 106, 201, 108, 188, 156, 75, 44, 232, 16, 145, 154, 47, 164, 23, 84, 58, 212, 185, 40, 171, 40, 43, 71, 140, 181, 236, 253, 13, 6, 143, 15, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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