Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b461e433a0f5602fd3dcc779cc126890eee63267a2873239f3765235daa4d9

Tx prefix hash: 5a5f820db23e062c40e02e3566ea25c64ba504903958a74d07c9b0467fe83db6
Tx public key: 3ec8772e3cafd584c33c12deef5a204ed923874ec70ab2c2fbcc1fd8b666a992
Timestamp: 1728569579 Timestamp [UCT]: 2024-10-10 14:12:59 Age [y:d:h:m:s]: 01:029:22:53:24
Block: 1128600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279779 RingCT/type: yes/0
Extra: 013ec8772e3cafd584c33c12deef5a204ed923874ec70ab2c2fbcc1fd8b666a992021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e193e282bb5926b271dff0fcd814345c04adb44aa91414e0a1ec68f6851a46a 0.600000000000 1611419 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": 1128610, "vin": [ { "gen": { "height": 1128600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e193e282bb5926b271dff0fcd814345c04adb44aa91414e0a1ec68f6851a46a" } } ], "extra": [ 1, 62, 200, 119, 46, 60, 175, 213, 132, 195, 60, 18, 222, 239, 90, 32, 78, 217, 35, 135, 78, 199, 10, 178, 194, 251, 204, 31, 216, 182, 102, 169, 146, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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